home *** CD-ROM | disk | FTP | other *** search
- Rick Adams and I (Donnalyn Frey) are currently preparing a
- completely new third edition of !%@:: A Directory of
- Electronic Mail Addressing and Networks, published by
- O'Reilly & Associates.
-
- When we originally published the book, we planned to update
- it regularly, but the complex formatting made that a much
- bigger job than originally anticipated. In order to make
- it possible to include updated information and new networks
- on a regular basis (every six months or so instead of every
- couple of years!), we're working on a new format that can
- be maintained largely automatically.
-
- What we've done is to prepare a template that you can fill
- in and e-mail to us, and which we can parse with simple
- scripts to produce the printed book. We may also make this
- information available on line in gopher format.
-
- This file explains the template and what we would like you to
- do. This message includes a sample template. A
- completely blank template follows. The completely blank
- template just contains headings in angle brackets, and the sample template
- is filled in with sample data. You can start
- from either copy, either filling in the blanks or
- overwriting the sample data with your own information.
-
- If some of the fields in the template are not appropriate
- for your network, please leave them blank. If you have
- additional information you think should be included, please
- include it in the section marked <EXTRAS>. Only you can choose
- what is most important for your network. However, PLEASE
- DON'T DELETE OR CHANGE ANY OF THE HEADINGS, since they are
- the "hooks" that our scripts will work from.
-
- For the people who have already sent network information to
- Donnalyn, thank you, but we ask you to do so again. Much
- of the material she has collected is now out of date, and
- we decided it would be easier to start over than to query
- everyone about what might or might not be correct. In this
- way, the information will be in the correct format, and is
- sure to be correct. For future editions, we will simply
- mail back to you your last revision for further updates.
-
- Please send the filled-in template to emaildir@ora.com
- (not to me). All information must be received by
- March 15 for publication in the next edition.
-
- If you have information on new networks that should be
- included in the book, please ask the network administrator
- to contact Donnalyn Frey or give Donnalyn an email address
- for the new network.
-
- If you have any questions, please contact Donnalyn Frey via
- email at donnalyn@frey.com, by fax at +1 703 204 8001, or
- by post at:
-
- Donnalyn Frey
- Frey Communications
- P.O. Box 2685
- Fairfax, VA 22031 USA
-
- Thank you for the information. We will send a
- complimentary copy of the new book to network
- administrators who provide information on their network
- which is used in the book.
-
-
- Here's an annotated example of the template. The headings,
- which you should leave intact, are contained in angle
- brackets (< and >). You can either overwrite this example
- with your own information, or fill in the completely blank
- template that follows it in a separate message. Thanks
- again for your help.
-
- Donnalyn Frey
-
-
- <NETSITE>
- <META>
- <NETWORKACRONYM>
- This field should contain the single-word acronym for your
- network, if such a thing exists. For example, for the
- South Korean Research and Academic Network, this field should
- read:
-
- SDN
-
- <NETWORKNAME>
- This field should contain the full name for the network. For
- example:
-
- South Korean Research and Academic Network
-
- <DESCRIPTION>
- This field should contain a brief one or two-paragraph overview of
- your network. For example:
-
- SDN is a Korean network available to research and academic
- organizations in South Korea. The network was begun in
- 1982. It is a segment of the Pacific network, PACNET.
-
- <FACILITIES>
- optional; a series of items describing the services offered by your
- network, one per line. For example:
-
- Electronic mail
- File Transfer
- Usenet news
-
- <ADDRESSING>
- Explain the general form of the addressing used in your network.
- Give the big picture here. Headings below will ask for
- examples and further details. For example:
-
- All computers on SDN use Internet-style domain-addresses.
- The network is also accessible via UUCP.
-
- The top-level domain is KR, with three major subdomains: AC
- (academic), CO (company) and RE (research).
-
- Each site has a postmaster account for inquiries on addresses
- and users.
-
- Please contact postmaster@host.domain. For example, to
- access the system manager at the computer of Hanyang University,
- send mail to postmaster@hyuee.hanyang.ac.kr. Host
- machines total approximately 100.
-
- If you use Internet style addressing, you should fill in
- the following domain information fields, as appropriate.
- The TOPDOMAIN field should identify the top-level country
- domain name. The SUBDOMAIN fields should list any next-
- level subdomains, one per line, with a brief explanation of
- each. If you have a list of actual sites, include that
- under the heading SITES.
-
- <TOPDOMAIN>
- KR (Korea)
-
- <SUBDOMAIN>
- ac (Academic)
- re (Research)
- co (Company)
-
- <SITES>
- Here, if known, provide a list of sites in each domain,
- including the site's domain name and the name of the
- organization that runs that site. For example:
-
- ora.com O'Reilly & Associates, Inc.
-
- <UUCP>
- If you are accessible by UUCP, give a well-connected UUCP
- path here. Repeat this heading as necessary for each
- well-connected path. For example:
-
- uunet!halla!site!user
- mcsun!halla!user
-
- <OTHER>
- optional, other addressing formats, such as EARN or Bitnet
- addresses.
-
- Close with any additional information you think might be
- appropriate, but that didn't fit in above. This might be
- appropriate if you don't use Internet addressing at all, or
- use some other addressing mechanism as well.
-
- The following tag marks the end of the addressing section. Don't
- enter
- anything here.
- </ADDRESSING>
-
- <CONTACT>
- This section includes information on who to contact for the
- network. Repeat these headings as needed if there are
- multiple contacts. Leave them blank if the information
- they ask for is not appropriate.
-
- <NAME>
- of the contact
-
- <POSTALADDRESS>
- of the contact
-
- <TELEPHONE>
- of the contact
-
- <TELEX>
- of the contact
-
- <FAX>
- of the contact
-
- <EMAIL>
- of the contact
-
- The following tag marks the end of the Contact information section.
- Don't enter anything here.
- </CONTACT>
- <CONNECTIONS>
- If there are any relevant connections to other networks or sites,
- mention that here.
-
- <FUTURE>
- If you have any future plans you want to communicate, describe them
- here.
-
- <UPDATED>
- enter the month and year you updated this file.
-
- <EXTRAS>
- Here include anything else you think we need to know, but
- which didn't fit into any of the categories above. Leave
- this field blank if you have nothing to add.
-
- <MAINTENANCEINFO>
- Here enter any information we might need for maintenance,
- but which should not appear in the book. This might
- include a private address, of contacts
-
- </NETSITE>
- <!-- end of template -->
-
-
-
-
-
- <NETSITE>
- <META>
- <NETWORKACRONYM>
-
-
- <NETWORKNAME>
-
-
- <DESCRIPTION>
-
-
- <FACILITIES>
-
-
- <ADDRESSING>
-
-
-
-
-
-
- <TOPDOMAIN>
-
- <SUBDOMAIN>
-
- <SITES>
-
-
- <UUCP>
-
-
- <OTHER>
-
-
- </ADDRESSING>
-
- <CONTACT>
-
- <NAME>
-
- <POSTALADDRESS>
-
- <TELEPHONE>
-
- <TELEX>
-
- <FAX>
-
- <EMAIL>
-
- </CONTACT>
- <CONNECTIONS>
-
- <FUTURE>
-
- <UPDATED>
-
- <EXTRAS>
-
- <MAINTENANCEINFO>
-
- </NETSITE>
- <!-- end of template -->
-